fix: .undefined
file extension when interacting with dir
directly
#288
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Starting with
v0.3.3
ifdir.ts
is called directly, like many consumers do, we would experience the.undefined
file extension issue. (#287).This is because prior
v0.3.3
the default extension was stored insidedir.ts
. So even though we have the defaults inoptions.ts
it will never reachdir.ts
.I see it as breaking change so this PR creates a constant (
DEFAULT_OUT_FILE_EXTENSION
) close to the options, that can also be used indir.ts
.The changes were tested through manual and automated tests (
yarn test
).